fix(sbom): preserve opaque bom-ref identity - #114
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Design decision
�om_ref is an opaque local identifier when no purl is present. Lowercasing it would merge distinct producer-local identifiers such as Component-A and component-a. Identity precedence remains purl -> �om_ref -> normalized coordinate.
Main risk
Existing inputs that relied on case-insensitive bom-ref matching can now produce separate components instead of an accidental merge. This is the intended fail-closed behavior for ambiguous local identifiers.
Compatibility impact
Purl-backed identities and coordinate fallback behavior are unchanged. The package remains at the already-established 1.1.0.dev0 development version; this PR does not create a release tag or publish artifacts.
Rollback path
Revert commit d3a9e9f if downstream evidence shows that case-insensitive bom-ref matching is an intentional producer contract.
Validation